Distributed package management using meta-scheduling

ABSTRACT

A system for package management includes an interface and a processor. The interface is to receive an indication to install a package. The processor is to determine a configured package using a set local configuration properties and using the package and to launch, using a metascheduler, a set of subschedulers to install a plurality of applications of the configured package.

CROSS REFERENCE TO OTHER APPLICATIONS

This application is a continuation of co-pending U.S. patent applicationSer. No. 15/829,740, entitled DISTRIBUTED PACKAGE MANAGEMENT USINGMETA-SCHEDULING, filed Dec. 1, 2017, which is a continuation of U.S.patent application Ser. No. 14/931,714, now U.S. Pat. No. 9,880,825,entitled DISTRIBUTED PACKAGE MANAGEMENT USING META-SCHEDULING, filedNov. 3, 2015, which claims priority to U.S. Provisional PatentApplication No. 62/202,047, entitled DISTRIBUTED PACKAGE MANAGEMENTUSING META-SCHEDULING, filed Aug. 6, 2015, each of which is incorporatedherein by reference for all purposes.

BACKGROUND OF THE INVENTION

Common software systems are increasingly distributed, composed ofmultiple software systems that execute simultaneously on many computers.These attributes complicate software lifecycle management, such asreliably distributing artifacts, launching, monitoring, and relaunchingsoftware processes. Traditional methods deal only with lifecyclemanagement on a single computer.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1 is a block diagram illustrating an embodiment of a system forinstallation and monitoring of packages on a cluster using ametascheduler.

FIG. 2 is a block diagram illustrating an embodiment of a systemcomprising a cluster manager.

FIG. 3 is a block diagram illustrating an embodiment of a system formanaging a cluster using a cluster manager.

FIG. 4 is a block diagram illustrating an embodiment of a packagerepository system as part of a cluster system.

FIG. 5 is a block diagram illustrating an embodiment of a packagerepository.

FIG. 6 is a block diagram illustrating an embodiment of a systemcomprising a cluster node with a metascheduler.

FIG. 7 is a block diagram illustrating an embodiment of a systemcomprising a cluster node as part of a cluster system for running amesos agent and a sub scheduler.

FIG. 8 is a block diagram illustrating an embodiment of a systemcomprising a cluster node as part of a cluster system for running amesos agent and package tasks.

FIG. 9 is a flow diagram illustrating an embodiment of a process forconfiguring and installing packages on a cluster system by launchingsubschedulers using a metascheduler.

FIG. 10 is a flow diagram illustrating an embodiment of a process formanaging a package.

FIG. 11 is a flow diagram illustrating an embodiment of a process forcausing an instantiation of a metascheduler.

FIG. 12 is a flow diagram illustrating an embodiment of a process forcausing an instantiation of a subscheduler.

FIG. 13 is a flow diagram illustrating an embodiment of a process forcausing an installation of a package.

FIG. 14 is a flow diagram illustrating an embodiment of a process forexecuting a task using the cluster.

FIG. 15 is a flow diagram illustrating an embodiment of a process forexecuting a task using the cluster.

FIG. 16 is a flow diagram illustrating an embodiment of a process forexecuting a task using the cluster.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess; an apparatus; a system; a composition of matter; a computerprogram product embodied on a computer readable storage medium; and/or aprocessor, such as a processor configured to execute instructions storedon and/or provided by a memory coupled to the processor. In thisspecification, these implementations, or any other form that theinvention may take, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered within thescope of the invention. Unless stated otherwise, a component such as aprocessor or a memory described as being configured to perform a taskmay be implemented as a general component that is temporarily configuredto perform the task at a given time or a specific component that ismanufactured to perform the task. As used herein, the term ‘processor’refers to one or more devices, circuits, and/or processing coresconfigured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

A system for package management is disclosed. The system comprises aninterface and a processor. The interface is to receive an indication toinstall a package. The processor is to determine a configured packageusing a set local configuration properties and using the package andlaunch using a metascheduler a set of subschedulers to install aplurality of applications of the configured package. In someembodiments, the system comprises a memory coupled to the processor andconfigured to provide the processor with instructions.

In some embodiments, a system for distributed package management usingmeta-scheduling is disclosed. The system comprises an interface and acollection of computer systems organized in a cluster system. Thecluster system comprises a cluster manager, a metascheduler node, apackage repository system, and a cluster. The cluster of the clustersystem comprises a plurality of computer systems referred to as clusternodes. The cluster manager comprises a command-line interface and aprocessor. In some embodiments, the cluster manager comprises aprocessor that runs software implementing cluster manager functionality.

In some embodiments, the command-line interface receives a selection ofsoftware packages to be installed on one or more cluster nodes in acluster. The processor iterates through the selection of softwarepackages. In some embodiments, the processor applies a localconfiguration to each selected software package to create a configuredsoftware package. In some embodiments, the processor sends theconfigured software packages to the metascheduler for installation onone or more cluster nodes. The metascheduler indicates to a number ofsubschedulers on one or more cluster nodes determined by the configuredsoftware package that the configured software package is to beinstalled. In some embodiments, each subscheduler receives additionalpackage data (e.g., installable software and application files) from apackage repository system. Each subscheduler installs the configuredsoftware package and additional package data on a cluster nodes.

In some embodiments, the system employs multi-tiered fault detection andcorrection. In some embodiments, the metascheduler reports the successor failure of its tasks to the cluster manager. In the event ofmetascheduler failure, the cluster manager is able to perform a remedialaction (e.g., restarting a computer system, relaunching a softwareapplication, and restarting the metascheduler). In some embodiments,each subscheduler reports the success or failure of its tasks to themetascheduler. In the event of task failure, the subscheduler is able toperform remedial action (e.g., restarting package installation) on itscluster node. In the event of subscheduler failure, the metascheduler isable to take remedial action (e.g., restarting the subscheduler,rebuilding the cluster node, or restarting package installation).

In some embodiments, each subscheduler monitors the performance andsuccess of applications running as part of the configured softwarepackage. In some embodiments, the configuration of the configuredsoftware package indicates performance parameters. When the performanceof applications running as part of the configured software package falloutside of the bounds of the indicated performance parameters, thesubscheduler can take remedial action to bring the performance ofapplications within the indicated performance parameters. In someembodiments, the remedial action includes instructing the metaschedulerto indicate the installation of the configured software package byadditional subschedulers. In some embodiments, the remedial actionincludes instructing the metascheduler to indicate the uninstallation ofthe configured software package on existing cluster nodes bysubschedulers.

In some embodiments, a package repository system comprises a packagerepository controller and a package repository. The package repositorystores unconfigured software packages. In some embodiments, anunconfigured software package contains data records as JSON-formattedfiles (e.g., command.json, config.json, marathon.json, and packagejson).In various embodiments, each data record in a software package comprisesone or more of the following: specific actions, configurable parameters,or any other appropriate other information. In some embodiments,command.json includes tasks that the configured software package willexecute on a cluster node. In some embodiments, package.json includesadditional software to be installed by the system. The packagerepository controller receives a request from a system for anunconfigured software package. The package repository controllerretrieves the unconfigured software package from the package repositoryand delivers it to the requesting system.

FIG. 1 is a block diagram illustrating an embodiment of a system forinstallation and monitoring of packages on a cluster using ametascheduler. In the example shown, cluster system 104 includes clustermanager 105, metascheduler node 106, package repository system 107, andcluster 108. Cluster system 104 is also coupled to network 103. Network104 enables user 100, user 101, and user 102 to connect to clustersystem 104. In some embodiments, user 100, user 101, and user 102communicate with cluster manager 105 using network 103. Cluster manager105 manages metascheduler node 106, package repository system 107,cluster 108, and other subsystems of cluster system 104. Metaschedulernode 106 comprises a node of the cluster that schedules subschedulers.Metascheduler node 106 is able to launch subscheduler(s) and is able todelete subscheduler(s). Metaschsuler node 106 is able to installapplications of a package on one or more nodes of cluster 108.Metascheduler node 106 stores/retrieves the package to/from packagerepository system 107.

FIG. 2 is a block diagram illustrating an embodiment of a systemcomprising a cluster manager. In some embodiments, cluster manager 200of FIG. 2 comprises cluster manager 105 of FIG. 1. In the example shown,cluster manager 200 includes command line interface 201 and mesos master202. Command-line interface 201 receives an instruction from a user toinstall a package. Metadata is retrieved from a package repositorysystem including configurable properties that the package supports.Configuration values are merged with the default values and are combinedwith template launch descriptors to generate a configured package thatis provided to a metascheduler by mesos master 202. The metaschedulerlaunches one or more subschedulers in the cluster. In the event that anyof the one or more subschedulers fails, the metascheduler can takeremedial action to start a new copy of the subscheduler and restart theprocess(es). The subscheduler registers with the cluster manager andinstalls applications and executes tasks to provide package services.The subscheduler automates and optimized operations includingautoscaling replicas (e.g., installing applications and executing taskson more cluster nodes or deleting them) to meet demand. Once the packagetasks are instantiated the subscheduler can monitor the tasks. In theevent that a task fails, the subscheduler can take remedial action(e.g., installing application and executing task on another clusternode).

FIG. 3 is a block diagram illustrating an embodiment of a system formanaging a cluster using a cluster manager. In some embodiments, cluster300 of FIG. 3 comprises cluster 108 of FIG. 1. In the example shown,cluster 300 comprises cluster network 307 and cluster nodes (e.g.,cluster node 301, cluster node 302, cluster node 303, cluster node 304,cluster node 305, etc.). Cluster manager communicates with cluster nodesof cluster 300 using cluster network 307. Cluster nodes of cluster 300and package repository system communicate with each other using clusternetwork 307. A cluster node is used for executing system processes. Invarious embodiments, a cluster node is used to execute a subscheduler, ametascheduler, a package task, or any other appropriate system process.

FIG. 4 is a block diagram illustrating an embodiment of a packagerepository system as part of a cluster system. In some embodiments,package repository system 401 of FIG. 4 comprises package repositorysystem 107 of FIG. 1. In the example shown, package repository system401 comprises package repository controller 402 and package repository403. Package repository 403 stores unconfigured software packages. Thesoftware packages can be configured and then provided to be installed.In various embodiments, configured packages are used to install a set ofapplications, a subscheduler, a metascheduler, a task executor, or anyother appropriate set of software.

FIG. 5 is a block diagram illustrating an embodiment of a packagerepository. In some embodiments, package repository 403 of FIG. 4comprises package repository 500 of FIG. 5. In the example shown,package repository 500 contains package 501, package 502, package 503,and package 504. In some embodiments, packages contain configurationfiles files (e.g., command.json, config.json, marathon.json, andpackagejson). In some embodiments, a command.json file describes how toinstall a package's CLI. For example, the file holds Python requirementsin order to get a package's command line interface working. In someembodiments, a config.json file has general properties and informationabout packages and sub schedulers. This can include information onrepeating tasks and how to determine whether failures are occurring. Insome embodiments, the information includes repeating tasks, prerequisitepackages, and resource requirements. In some embodiments, theinformation includes services that are run and monitored. In someembodiments, a marathon.json file is a configuration for ametascheduler. The metascheduler is used to launch new services/tasks ascluster nodes. In some embodiments, a package.json file includesspecific information about the subscheduler/package to be installed. Insome embodiments, the information includes information to display to theuser, such as package descriptions, home pages for packages, tags, andversion numbers. In various embodiments, the information includes one ormore of the following: package name, package version, package sourcelocation, package maintainer, package description, package identifier(e.g., scheduler or not), package images, package licenses, package tags(e.g., for searching), package pre-install notes (e.g., to be shown inthe CLI before installation), package post-install notes (e.g., to beshown after the CLI has completed installation), package post-uninstallnotes (to be shown after the CLI has completed uninstallation), or anyother appropriate information.

FIG. 6 is a block diagram illustrating an embodiment of a systemcomprising a cluster node with a metascheduler. In some embodiments,cluster node 600 of FIG. 6 comprises cluster nodes 301, cluster node302, cluster node 303, cluster node 304, or cluster node 305 of FIG. 3.In the example shown, cluster node 600 includes metascheduler 601.Metascheduler 601 is a scheduler that manages other schedulers (e.g.,subschedulers). Metascheduler 601 and subscheduler(s) form a supervisoryhierarchy, separating the concerns of maintaining a highly-availablescheduler, and coordinating package processes. The supervisoryrelationship allows for advanced self-healing properties. Themetascheduler regularly queries subschedulers regarding both the healthof the subscheduler and the health of package services. For example, ifthe subscheduler is unable to communicate with the cluster manager, itmay report an unhealthy status, prompting metascheduler to kill thatprocess and launches a new instance elsewhere in the cluster.

In some embodiments, metascheduler 601 registers with a cluster managerand is monitored by the cluster manager. In the event that metascheduler601 fails or is unresponsive, the cluster manager kills that process andlaunches a new instance elsewhere in the cluster.

In some embodiments, registration includes providing information formonitoring and enabling restarting of a process. For example, a process(e.g., a subscheduler, a metascheduler, a task process, etc.) registerswith a cluster manager or another cluster process (e.g., ametascheduler, a sub scheduler, a task process, etc.) so that theprocess can be monitored to make sure that it is functioning properly.In the event that the process has an error, the error can be detected,the process can be terminated, and the process can be restarted. Invarious embodiments, the registration information includes one or moreof the following:

-   -   User: the user account to run the scheduler under, used for        authorization    -   Name: name of scheduler, reference in user interface (UI) and        endpoints    -   ID: unique identifier (Name is not necessarily unique), used as        reference in the UI and endpoints    -   Failover timeout: the amount of time to wait before destroying        the scheduler's tasks    -   Checkpoint: in the event that a task process goes down a        checkpoint allows the recovery of the sub scheduler's task    -   Role: allows a subscheduler to utilize a bucket of resources,        buckets are referenced by name, a subscheduler can register to        receive resources by setting its role    -   Hostname: the hostname that the subscheuler is running on    -   Webui_url: the location that the webui is running at. UI uses to        forward users from the metascheduler to a subscheduler    -   Capabilities: list of capabilities that the subscheduler        supports (e.g., revocable resources, etc.)    -   Labels: list of labels in key/value pair format allowing        subschedulers to add metadata    -   Any other appropriate information        In some embodiments, information for restarting the process is        not in the registration information. In some embodiments, the        restart information is exchanged and stored with a cluster unit        (e.g., a metascheduler, a subscheduler, a task process, a        cluster manager, etc.). In some embodiments, the restart        information is exchanged when the subscheduler is added to the        metascheduler, the metascheduler stores the restart information,        and the metascheduler restarts a subschedulers when an error        occurs.

In some embodiments, a cluster manager registers with metascheduler 601and is monitored by metascheduler 601. In the event that the clustermanager fails or is unresponsive, the metascheduler 601 kills thatprocess and launches a new instance elsewhere in the cluster.

FIG. 7 is a block diagram illustrating an embodiment of a systemcomprising a cluster node as part of a cluster system for running amesos agent and a subscheduler. In some embodiments, cluster node 700 ofFIG. 7 comprises cluster node 301, cluster node 302, cluster node 303,cluster node 304, or cluster node 305 of FIG. 3. In the example shown,cluster node 700 includes mesos agent 702 and subscheduler 704. Ametascheduler launches subscheduler 704 via a cluster manager and usingmesos agent 702.

In some embodiments, subscheduler 704 registers with a cluster managerand is monitored by the cluster manager. In the event that subscheduler704 fails or is unresponsive, the cluster manager kills that process andlaunches a new instance elsewhere in the cluster.

FIG. 8 is a block diagram illustrating an embodiment of a systemcomprising a cluster node as part of a cluster system for running amesos agent and package tasks. In some embodiments, cluster node 800 ofFIG. 8 comprises cluster node 301, cluster node 302, cluster node 303,cluster node 304, or cluster node 305 of FIG. 3. In the example shown,cluster node 800 includes mesos agent 802 and package task 804. Asubscheduler launches package task 804 and monitors and controls taskexecution. In various embodiments, in the event that tasks fail torespond, tasks are running slowly, tasks executers are idle, thesubscheduler kills task executers, launches more task executers, or anyother appropriate action.

In some embodiments, executing tasks register with a cluster manager andare monitored by the cluster manager as well as a subscheduler. In theevent that the subscheduler fails or is unresponsive, the clustermanager kills that process and launches a new instance elsewhere in thecluster as well as the executing tasks.

FIG. 9 is a flow diagram illustrating an embodiment of a process forconfiguring and installing packages on a cluster system by launchingsubschedulers using a metascheduler. In some embodiments, the process ofFIG. 9 is executed using the system of FIG. 1. In the example shown, in900, an indication to install a package is received. For example, acluster manager receives a request to install a package. In 902, localconfiguration properties are received. For example, the localconfiguration properties are stored in a j son file that is created bythe end user and passed to the CLI using a command line argument. In904, a package is configured using the local configuration properties.For example, a package as stored in a package repository is retrievedand configured using a set of local configuration properties. In 906,the system causes the launch of subscheduler(s) to install theapplication of the configured package using a metascheduler, and theprocess ends.

FIG. 10 is a flow diagram illustrating an embodiment of a process formanaging a package. In some embodiments, the process of FIG. 10 isimplemented 906 of FIG. 9. In the example shown, in 1000 aninstantiation of a metascheduler is caused. For example, a clustermanager causes the instantiation of a metascheduler on a cluster node.In 1002, an instantiation of subscheduler(s) is/are caused. For example,a cluster manager causes the instantiation of one or more subschedulersby requesting that the metascheduler instantiate the one or moresubschedulers. In 1004, an installation is caused for a configuredpackage using a subscheduler. For example, a cluster manager causes theinstallation of a configured package on one or more agents using the oneor more subschedulers.

FIG. 11 is a flow diagram illustrating an embodiment of a process forcausing an instantiation of a metascheduler. In some embodiments, theprocess of FIG. 11 is used to implement 1000 of FIG. 10. In the exampleshown, in 1100 an installation package for metascheduler is provided. In1102, installation of metascheduler is launched. In 1104, it isdetermined whether the installation is proceeding without error. In theevent that installation is not proceeding without error, in 1108remedial action is performed to continue to install the metascheduler,and control passes 1104. In the event that installation is proceedingwithout error, in 1106 it is determined whether installation iscomplete. In the event that installation is not complete, then controlpasses to 1104. In the event that installation is complete, then processends.

FIG. 12 is a flow diagram illustrating an embodiment of a process forcausing an instantiation of a subscheduler. In some embodiments, theprocess of FIG. 12 is used to implement 1002 of FIG. 10. In the exampleshown, in 1200 an installation package for subscheduler(s) is received.In 1202, installation of subscheduler(s) is/are launched. In 1204, it isdetermined whether the installation is proceeding without error. In theevent that installation is not proceeding without error, in 1208remedial action is performed to continue to install the subscheduler(s),and control passes 1204. In the event that installation is proceedingwithout error, in 1206 it is determined whether installation iscomplete. In the event that installation is not complete, then controlpasses to 1204. In the event that installation is complete, then processends.

FIG. 13 is a flow diagram illustrating an embodiment of a process forcausing an installation of a package. In some embodiments, the processof FIG. 13 is used to implement 1004 of FIG. 10. In the example shown,in 1300 configured package for application installation is provided. In1302, application installation(s) is/are launched. In 1304, it isdetermined whether the installation is proceeding without error. In theevent that installation is not proceeding without error, in 1308remedial action is performed to continue to install the application(s),and control passes 1304. For example, installation of the application ismonitored using the subscheduler, and upon failure, the installationprocess is killed and restarted. In the event that installation isproceeding without error, in 1306 it is determined whether installationis complete. In the event that installation is not complete, thencontrol passes to 1304. In the event that installation is complete, thenprocess ends.

FIG. 14 is a flow diagram illustrating an embodiment of a process forexecuting a task using the cluster. In the example shown, in 1400 anindication to execute a task is received. In 1402, task is provided tometascheduler for execution using agent(s) directed by subschedulers.For example, the cluster manager provides the metascheduler a task. In1404, it is determined whether metascheduler is proceeding withouterror. In the event that metascheduler is not proceeding without error,in 1408 remedial action is performed to continue metascheduler, andcontrol passes 1404. For example, the cluster manager monitors themetascheduler and detects failure, kills the metascheduler process, andrestarts the metascheduler. In the event that installation is proceedingwithout error, in 1406 it is determined whether task is complete. In theevent that task is not complete, then control passes to 1404. In theevent that the task is complete, then in 1410 task result(s) is/arereceived. For example, task results are generated by agents performingtask and passed to a subscheduler, a metascheduler, and/or the clustermanager. In 1412, task result(s) are provided. For example, the taskresults are provided to the requestor that requested to execute thetask.

FIG. 15 is a flow diagram illustrating an embodiment of a process forexecuting a task using the cluster. In some embodiments, the process ofFIG. 15 is used to implement 1402 of FIG. 14. In the example shown, in1500 an indication to execute a task is received. For example,metascheduler receives indication to execute a task. In 1502, task isprovided to a subscheduler for execution using agent(s). In 1504, it isdetermined whether subscheduler is proceeding without error. Forexample, the metascheduler monitors one or more subschedulers or a setof subschedulers associated with task execution. In the event thatsubscheduler is not proceeding without error, in 1508 remedial action isperformed to continue subcheduler, and control passes 1504. For example,the metascheduler monitors the set of subschedulers associated withperforming a task, detects a failure of a subscheduler, kills thesubscheduler process, and restarts the subscheduler. In the event thatsubscheduler is proceeding without error, in 1506 it is determinedwhether task is complete. In the event that task is not complete, thencontrol passes to 1504. In the event that the task is complete, then in1510 task result(s) is/are received from sub scheduler. In 1512, taskresult(s) are provided to cluster manager. For example, the task resultsare provided to the requestor that requested to execute the task byproviding them to the cluster manger and then to the requestor.

FIG. 16 is a flow diagram illustrating an embodiment of a process forexecuting a task using the cluster. In some embodiments, the process ofFIG. 16 is used to implement 1502 of FIG. 15. In the example shown, in1600 an indication to execute a task is received. For example,subscheduler receives indication to execute a task. In 1602, task isprovided to agent(s). In 1604, it is determined whether agent(s) is/areproceeding without error. In the event that agent(s) is/are notproceeding without error, in 16016 remedial action is performed tocontinue execution of task, and control passes 1604. For example, thesubscheduler monitors performance of application when executing a task,and upon detecting an error, kills the task process, and restarts theprocess (e.g., in the same agent, a different agent, etc.). In the eventthat agent(s) is/are proceeding without error, in 1606 it is determinedwhether task execution is underperforming. In the event that taskexecution is underperforming, in 1618 it is indicated to use moreagent(s) to execute the task, and control passes to 1610. In the eventthat task execution is not underperforming, then in 1608 it isdetermined whether there is/are agent(s) idle. In the event thatagent(s) is/are idle, then in 1620 it is indicated to terminate idleagent(s), and control passes to 1610. In the event that agent(s) is/arenot idle, then in 1610 it is determined whether task is complete. In theevent that task is not complete, then control passes to 1604. In theevent that the task is complete, then in 1612 task result(s) is/arereceived from agent(s). In 1614, task result(s) are provided to metascheduler. For example, the task results are provided to the requestorthat requested to execute the task by determining the results using anagent and providing them to the subscheduler, to the metascheduler, tothe cluster manager, and then to the requestor.

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive.

What is claimed is:
 1. (canceled)
 2. A system for package management,comprising: an interface to: receive an indication to install a package;and a processor configured to: determine a configured package using aset local configuration properties and using the package; launch, usinga metascheduler, a set of subschedulers to install a plurality ofapplications of the configured package; monitor the set of subschedulersand the metascheduler; and perform a remedial action based on a resultof the monitoring.
 3. A system as in claim 2, wherein monitoring the setof subschedulers detects a failure of a subscheduler of the set ofsubschedulers.
 4. A system as in claim 3, wherein the remedial actionincludes the metascheduler restarting the subscheduler in the event thatthe failure of the sub scheduler is detected.
 5. A system as in claim 2,wherein processor comprises a processor of a cluster manager of acluster.
 6. A system as in claim 5, wherein monitoring the metaschedulerdetects a failure of the metascheduler.
 7. A system as in claim 6,wherein the remedial action includes the cluster manager restarting themetascheduler in the event that the failure of the metascheduler isdetected.
 8. A system as in claim 2, wherein a subscheduler is executedusing a cluster node of a cluster.
 9. A system as in claim 8, whereinthe subscheduler installs an application of the plurality of applicationof the configured package on one or more nodes of the cluster.
 10. Asystem as in claim 9, wherein the subscheduler monitors the installationof the application.
 11. A system as in claim 10, wherein monitoring theinstallation detects a failure to install the application.
 12. A systemas in claim 11, wherein the subscheduler restarts the installation ofthe application in the event that the failure to install the applicationis detected.
 13. A system as in claim 9, wherein the subschedulermonitors performance of the application when executing a task.
 14. Asystem as in claim 13, wherein monitoring the performance of theapplication detects a failure of the application.
 15. A system as inclaim 13, wherein monitoring the performance of the application detectsunder performance.
 16. A system as in claim 13, wherein monitoring theperformance of the application detects idle resources.
 17. A method ofpackage management, comprising: receiving an indication to install apackage; determining, using a processor, a configured package using aset local configuration properties and using the package; launching,using a metascheduler, a set of subschedulers to install a plurality ofapplications of the configured package; monitoring the set ofsubschedulers and the metascheduler; and performing a remedial actionbased on a result of the monitoring.
 18. A computer program product forpackage management, the computer program product being embodied in anon-transitory computer readable storage medium and comprising computerinstructions for: receiving an indication to install a package;determining a configured package using a set local configurationproperties and using the package; launching, using a metascheduler, aset of subschedulers to install a plurality of applications of theconfigured package; monitoring the set of sub schedulers and themetascheduler; and performing a remedial action based on a result of themonitoring.